-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(header): properly support the Icon
interface
#3421
Conversation
ad6c07a
to
26ddcaa
Compare
Documentation has been published to https://lundalogik.github.io/lime-elements/versions/PR-3421/ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is the correct way to move forward, for all components, and get rid of all those silly and old CSS props. But I cannot merge this PR, it needs some blessings from @adrianschmidt @jgroth
I'll have a look 👍 |
Now the consumer can specify `color` and `backgroundColor` directly on the `icon`. The styles code are however backwards compatible, and still support the old custom CSS props of `--header-icon-color` and `--header-icon-background-color`. In case any consumer has specified the CSS props, they will get the same result as before. But we removed the props from the documentations, since we want the consumers to use the `Icon` interface instead of adding styles.
26ddcaa
to
75f01bf
Compare
The changes to It seems like once that file has been touched in a PR, the PR requires a review from a maintainer, even if those changes are then removed from the PR. So if you want to avoid having to wait for a maintainer for no good reason, keep an eye on what you push 😊 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Rubberstamp
🎉 This PR is included in version 37.81.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Now the consumer can specify
color
andbackgroundColor
directly on theicon
. The styles code are however backwards compatible, and still support the old custom CSS props of--header-icon-color
and--header-icon-background-color
. In case any consumer has specified the CSS props, they will get the same result as before. But we removed the props from the documentations, since we want the consumers to use theIcon
interface instead of adding styles.Review:
Browsers tested:
(Check any that applies, it's ok to leave boxes unchecked if testing something didn't seem relevant.)
Windows:
Linux:
macOS:
Mobile: